use core::dependency::SerializedDependency;
use util::{CargoResult, human};
-/// Contains all the informations about a package, as loaded from a Cargo.toml.
+/// Contains all the information about a package, as loaded from a Cargo.toml.
#[derive(Clone, Debug)]
pub struct Manifest {
summary: Summary,
pub custom_build: Profile,
}
-/// Informations about a binary, a library, an example, etc. that is part of the
+/// Information about a binary, a library, an example, etc. that is part of the
/// package.
#[derive(Clone, Hash, PartialEq, Eq, Debug)]
pub struct Target {
//! * Never try to activate a crate version which is incompatible. This means we
//! only try crates which will actually satisfy a dependency and we won't ever
//! try to activate a crate that's semver compatible with something else
-//! activatd (as we're only allowed to have one).
+//! activated (as we're only allowed to have one).
//! * Always try to activate the highest version crate first. The default
//! dependency in Cargo (e.g. when you write `foo = "0.1.2"`) is
//! semver-compatible, so selecting the highest version possible will allow us
}
```
-This build script starts out by compiling out C file into an object file (by
+This build script starts out by compiling our C file into an object file (by
invoking `gcc`) and then converting this object file into a static library (by
invoking `ar`). The final step is feedback to Cargo itself to say that our
output was in `out_dir` and the compiler should link the crate to `libhello.a`
While they _can_, strictly speaking, they should not. A version requirement
of `*` says “This will work with every version ever,” which is never going
-to be true. Libraries should always specifiy the range that they do work with,
+to be true. Libraries should always specify the range that they do work with,
even if it’s something as general as “every 1.x.y version.”
# Why `Cargo.toml`?